question

Julio R avatar image
1 Like"
Julio R asked Julio R commented

Travel problem

I have this model where sometimes I have a error message. This happens in a larger model but I was able to reproduce it in a smaller one.

The problem does not happens always in the same time and sometimes it does not happens (even with the repeat random streams activated)

I suspect it has something to do with traveling to an object inside another object that is in a queue and using network nodes. If this was not permitted I would not be suprise since is something that seems to not be so well design, but Im courious why it works hundreds of times and then it does not work.

It seems the run speed increases the chance of happening but I am not sure of this.

Why may this be happening?

Error travels.fsm

FlexSim 24.0.0
travelnetwok nodes
error-travels.fsm (37.6 KiB)
· 1
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jason Lightfoot avatar image Jason Lightfoot ♦♦ commented ·

Is it this message?

time: 55511.649662 exception: Exception Caught in NetworkNavigator::queryDistanceEx(TaskExecuter* te, FlexSimObject* destobj, NetworkNode* originnetnode, NetworkNode** bestorigin DEFAULTNULL, NetworkNode** bestdestnode DEFAULTNULL, int * bestoriginrow DEFAULTNULL, int * bestdestcol DEFAULTNULL, double* bestdist DEFAULTNULL) object: /DefaultNetworkNavigator
time: 55511.649662 exception: Exception Caught in NetworkNavigator::navigateToObject(treenode traveler, treenode destination, double endspeed) object: /DefaultNetworkNavigator
time: 55511.649662 exception: Exception Caught in ObjectFunction250__project_library_FlexSimObject_behaviour_eventfunctions_OnTimerEvent object: /Transporter1 i: /Transporter1>variables/coordinatedtasks/ts4208/task1 class: /Transporter1
0 Likes 0 ·
Phil BoBo avatar image
1 Like"
Phil BoBo answered Julio R commented

I haven't debugged exactly what's causing the exception, but you can work around it by traveling to an object connected to the network rather than traveling to an item and having the navigator try to determine how that item is connected to the network.

Specifically: on your Travel activity, pass token.item.up as the Object rather than token.item. The queue (token.item.up) has a blue line to the network, not the pallet (token.item). Pass the queue as the object to travel to.

· 1
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Julio R avatar image Julio R commented ·

Thank you!

That was my solution, I think is normal for this to not work since I am traveling to an item insde another item inside a queue, not the most standard thing to do, I was more curious about why it worked most times.

Thanks again!

0 Likes 0 ·
Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered

I've confirmed the issue and will send it to the developers - thank you for pointing it out to us.

5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.